serviceability: expose public fn to calculate access pass airdrop target#3909
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
airdrop_user_target_lamports(rent, user_airdrop_lamports, multiplier)fromairdrop_user_creditsin the serviceability program, so the feed oracle can compute the expected access pass airdrop target without duplicating the program's math.&Rentrather than callingRent::get()internally, so it works both on-chain (caller passesRent::get()?) and off-chain whereRentis fetched over RPC (getMinimumBalanceForRentExemptionor the rent sysvar account).airdrop_user_creditsnow delegates the target calculation to the new function, then subtracts the current balance and transfers the difference. Its signature and behavior are unchanged, so the three existing call sites are untouched.Testing Verification
minimum_balance(AIRDROP_USER_RENT_LAMPORTS_BYTES) + user_airdrop_lamportsformultiplier = 1, and that result scaled byNformultiplier = N.cargo test -p doublezero-serviceability), confirming the refactor preserves the airdrop transfer behavior.